Minor doc tweaks on Garmin GPI.

diff --git a/xmldoc/formats/garmin_gpi.xml b/xmldoc/formats/garmin_gpi.xml
index 43a1657382fc8a44d44e6eba215d0da526584a44..5472e78593758c3a4ace8aab3b27fe3db8030f46 100644 (file)
--- a/xmldoc/formats/garmin_gpi.xml
+++ b/xmldoc/formats/garmin_gpi.xml
@@ -1,7 +1,7 @@
 <para>
-   The format garmin_gpi supports binary POI (.gpi) files useable
-   on newer Garmin GPS receivers (see also <link linkend="fmt_garmin_poi">garmin_poi</link> for some hints).
-   <ulink url="http://www.garmin.com/support/agree.jsp?id=927">Garmin POI-Loader</ulink> is the standard application that creates GPI's
+   The format garmin_gpi supports the binary POI (.gpi) files that are useable
+   on newer Garmin GPS receivers.  See <link linkend="fmt_garmin_poi">garmin_poi</link> for additional information about Garmin's own Poiloader program.
+   <ulink url="http://www.garmin.com/support/agree.jsp?id=927">Garmin POI-Loader</ulink> is the standard application that creates GPI files
    with all possible features.
 </para>
 <para>
@@ -21,7 +21,7 @@
        This module does not support direct transfer of .GPI files to
        receivers in Garmin protocol mode.  For units like Nuvi, Zumo, or 
        Streetpilot, just choose a file that's on the drive where your
-       GPS is mounted.   For units like the X series (GPSMap60, etc.) 
+       GPS is mounted.   For units like the X series (GPSMap 60CSx, GPSMap 60Cx, Legend Hcx, etc.) 
        you must explictly put the unit in mass storage mode or mount
        the memory chip in an external reader and transfer the file 
        directly.

diff --git a/xmldoc/formats/options/garmin_gpi-proximity.xml b/xmldoc/formats/options/garmin_gpi-proximity.xml
index 1912172c086aeebec3e7b0e35387eb528e6ab08e..7b3d5191718867d40f391980a285e05b9f51cb5f 100644 (file)
--- a/xmldoc/formats/options/garmin_gpi-proximity.xml
+++ b/xmldoc/formats/options/garmin_gpi-proximity.xml
@@ -1,13 +1,16 @@
 <para>
-  When no proximity data is available GPSBabel uses this as default proximity value.
+  When no proximity data is available in the source input, GPSBabel uses this as the default proximity value.
   The parameter has to be in meters, or, when units=s specified, in miles.
   <link linkend="fmt_garmin_gpi_o_alerts">alerts</link> are automatically enabled.
 </para>
+<example id="garmin_gpi_speedcams">
+<title>Read GPX file, create GPI to alert when you're 1/2 mile from a speed camera.</title>
 <para>
   <userinput>
     gpsbabel -i gpx -f "SpeedCameras.gpx" -o garmin_gpi,units=s,proximity=0.5 -F "SpeedCameras.gpi"
   </userinput>
 </para>
+</example>
 <para>
   Its also possible to append a specific distance unit to the parameter.
 </para>

diff --git a/xmldoc/formats/options/garmin_gpi-sleep.xml b/xmldoc/formats/options/garmin_gpi-sleep.xml
index a852677e70107b6a2d9c190ad78c0409c4e061f8..5707e3a169f642f113b36f593bb004f6981f60c8 100644 (file)
--- a/xmldoc/formats/options/garmin_gpi-sleep.xml
+++ b/xmldoc/formats/options/garmin_gpi-sleep.xml
@@ -1,13 +1,13 @@
 <para>
-  Garmin units seems to use the creation timestamp of GPI files for internal jobs. 
+  Garmin unit seems to use the creation timestamp of GPI files for internal purposes. 
   In other words,  if you load GPI files with same creation timestamp on your device, 
-  strange things will happen (missing or repeated POIs). With sleep GPSbabel waits a given
+  strange things will happen (missing or repeated POIs). With the sleep option, GPSbabel waits a given
   number of seconds after the GPI file was written.
 </para>
 <para>
-  In normal case, when using GPSBabel from commandline or from the GUI, the chance to get files
-  with same timestamp is in the nearly ZERO. In scripts or batch files this looks quiet other.
-  Here we suggess the use of the sleep option. Values can be 1 (second) or more.
+  In the normal case of using GPSBabel from commandline or from the GUI, the chance of creating files
+  with the same timestamp is in the nearly ZERO. In scripts or batch files where you are writing multiple files - even from different GPSBabel instances - the odds of this happening is rather good.
+  The sleep option forces GPSBabel to wait after creating a file to ensure the timestamps are unique. Values are specified in seconds and can be 1 or more.
 </para>
 <para>
   <userinput>

diff --git a/xmldoc/formats/options/garmin_gpi-speed.xml b/xmldoc/formats/options/garmin_gpi-speed.xml
index 4c23a684e83b0f10139a04b78afb47bef807c943..61ca356815d0fae7dd8fc8cbfb8d90a6e8d79d87 100644 (file)
--- a/xmldoc/formats/options/garmin_gpi-speed.xml
+++ b/xmldoc/formats/options/garmin_gpi-speed.xml
@@ -1,5 +1,5 @@
 <para>
-  When no speed data is available GPSBabel uses this as default speed value.
+  When no speed data is available in the source input, GPSBabel uses this as the default speed value.
   The parameter has to be in kilometers per hour, or, when units=s specified,
   in miles per hour. <link linkend="fmt_garmin_gpi_o_alerts">alerts</link> are
   automatically enabled.